With the updates to the document generation capabilities and framework in 10.3.0, previous rulebases designed to perform document generation will no longer function out of the box. In order to get these rulebases working two steps must be performed, outlined below.
Previously, where all of the information required for the document generation process was stored against the Summary screen link, this changed in 10.3.0 with the introduction of Document objects to the Screens file.
When a rulebase authored pre-10.3.0 is loaded, the user will be prompted to upgrade in order to continue working with the rulebase. Part of this upgrade process moves the document generation configuration parameters from the Document link on the Summary screen to Custom Properties of newly created Document objects.
The most important custom property is XSLT_File, which defines where the XSLT file used to generate the document can be found. As with other template paths this is relative to the root of the rulebase archive.
Note: if your deployment does not support automatic introspection and loading of plugins you may need to perform additional configuration steps.
This plugin alone is not enough to enable legacy document generation. The plugin itself relies on the Apache FOP engine, available from http://xmlgraphics.apache.org/fop/, and has been tested with version 0.95. Once the fop.jar file and its dependencies have been downloaded, place it in your \WEB-INF\lib\ directory to ensure it is detected.
This plugin alone though is not enough to enable Legacy Document Generation. The plugin itself relies on the nFop engine, available from http://sourceforge.net/projects/nfop/, and has been tested with version 1.0.0. Once the fop.net.dll file has been downloaded, place it in your \bin\ directory to ensure it is detected.